Problem Note 40524: "Segmentation Violation In Task [ RISK ]" occurs before instrument pricing when no output variables are declared
When running a SAS® Risk Dimensions® analysis project, you might encounter the following error message in the SAS log:
Segmentation Violation In Task [ RISK ]
Fault and traceback information not available
Task Traceback
The segmentation violation is a generic error for which there are many possible causes and no single remedy. However, the location of this message in the SAS log and the configuration specifications for the risk environment could offer insight regarding the source of the problem and how to avoid it.
If the segmentation violation occurs prior to the instrument pricing of the analysis project, and if your risk environment does not have any output variables declared, then this segmentation violation could be due to a problem with the way output variables are handled when no output variables are included in an analysis project.
To circumvent this problem, ensure that your risk analysis project has output variables associated to it. In other words, the analysis project needs to have at least one output variable declared and it needs to use the output variable during the processing of the analysis project.
If your project does not otherwise need any output variables, then you can declare a dummy post-VaR output variable. If you specify the following SAS code prior to the RUNPROJECT statement in PROC RISK and within the same risk environment as the analysis project, then this will ensure that an output variable is associated to the project in order to avoid the segmentation violation that is described above:
declare outvars=(outvdummy num computed postvar);
Operating System and Release Information
SAS System | SAS Risk Dimensions Enterprise Edition | Microsoft Windows 2000 Server | 4.2.1 | | 9.1 TS1M3 SP4 | |
Microsoft Windows 2000 Datacenter Server | 4.2.1 | | 9.1 TS1M3 SP4 | |
Microsoft Windows 2000 Advanced Server | 4.2.1 | | 9.1 TS1M3 SP4 | |
Microsoft Windows 2000 Professional | 4.2.1 | | 9.1 TS1M3 SP4 | |
Microsoft Windows NT Workstation | 4.2.1 | | 9.1 TS1M3 SP4 | |
Microsoft Windows Server 2003 Datacenter Edition | 4.2.1 | 5.2 | 9.1 TS1M3 SP4 | 9.2 TS2M0 |
Microsoft Windows Server 2003 Enterprise Edition | 4.2.1 | 5.2 | 9.1 TS1M3 SP4 | 9.2 TS2M0 |
Microsoft Windows Server 2003 Standard Edition | 4.2.1 | 5.2 | 9.1 TS1M3 SP4 | 9.2 TS2M0 |
Microsoft Windows XP Professional | 4.2.1 | 5.2 | 9.1 TS1M3 SP4 | 9.2 TS2M0 |
Windows Vista | 4.2.1 | 5.2 | 9.1 TS1M3 SP4 | 9.2 TS2M0 |
Windows Vista for x64 | 4.2.1 | 5.2 | 9.1 TS1M3 SP4 | 9.2 TS2M0 |
64-bit Enabled AIX | 4.2.1 | 5.2 | 9.1 TS1M3 SP4 | 9.2 TS2M0 |
64-bit Enabled HP-UX | 4.2.1 | 5.2 | 9.1 TS1M3 SP4 | 9.2 TS2M0 |
64-bit Enabled Solaris | 4.2.1 | 5.2 | 9.1 TS1M3 SP4 | 9.2 TS2M0 |
HP-UX IPF | 4.2.1 | 5.2 | 9.1 TS1M3 SP4 | 9.2 TS2M0 |
Linux | 4.2.1 | 5.2 | 9.1 TS1M3 SP4 | 9.2 TS2M0 |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.
Type: | Problem Note |
Priority: | high |
Date Modified: | 2010-08-05 16:05:28 |
Date Created: | 2010-08-05 09:57:51 |